Micron Document




Outline of software engineering
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
top
The following outline is provided as an overview of and topical guide to software engineering:

Software engineering – application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software; that is the application of engineering to software.cite-ref-1[1]

The ACM Computing Classification system is a poly-hierarchical ontology that organizes the topics of the field and can be used in semantic web applications and as a de facto standard classification system for the field. The major section "Software and its Engineering" provides an outline and ontology for software engineering.

Contents


──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Software applications

Software engineers build software (applications, operating systems, system software) that people use.

Applications influence software engineering by pressuring developers to solve problems in new ways. For example, consumer software emphasizes low cost, medical software emphasizes high quality, and Internet commerce software emphasizes rapid development.




Data mining closely related to database

Airline reservations

Cheque processing


Trade
Auctions (e.g. eBay)
Reverse auctions (procurement)


Parsers
Linkers
Loaders


E-mail
VOIP
Calendars — scheduling and coordinating


Special effects for video and film
Editing
• Post-processing

Databases, support almost every field
Embedded systems Both software engineers and traditional engineers write software control systems for embedded products.

• Automotive software
• Heating ventilating and air conditioning (HVAC) software

Engineering All traditional engineering branches use software extensively. Engineers use spreadsheets, more than they ever used calculators. Engineers use custom software tools to design, analyze, and simulate their own projects, like bridges and power lines. These projects resemble software in many respects, because the work exists as electronic documents and goes through analysis, design, implementation, and testing phases. Software tools for engineers use the tenets of computer science; as well as the tenets of calculus, physics, and chemistry.


File

FTP



Games

Poker

Information systems, support almost every field

LIS Management of laboratory data
MIS Management of financial and personnel data





Music





Routers





Signal processing, encoding and interpreting signals

Image processing, encoding and interpreting visual information

Simulation, supports almost every field.

Engineering, A software simulation can be cheaper to build and more flexible to change than a physical engineering model.



• Traffic Control



Drill
• Testing

Visualization, supports almost every field


Voting

Servers

Software engineering topics

| Programming languages | Programming languages | Programming languages | Programming languages |
|---|---|---|---|
| Ada | APL | B | |
| COBOL | Pascal | C | C++ |
| C# | Clojure | Common Lisp | D |
| ColdFusion | Delphi | Dylan | Eiffel |
| Erlang | Fortran | F# | Groovy |
| Java | Lasso | ML | OCaml |
| Perl | PHP | PL/SQL | Prolog |
| Go | Rust | Swift | JavaScript |
| Haskell | Python | Ruby | Scala |
| Scheme | Smalltalk | Tcl | T-SQL |
| Verilog | VHDL | Visual Basic | Visual Basic .NET |
| Assembly language • • • Scripting language • • • List of programming languages | Assembly language • • • Scripting language • • • List of programming languages | Assembly language • • • Scripting language • • • List of programming languages | Assembly language • • • Scripting language • • • List of programming languages |

Programming paradigm, based on a programming language technology
Databases

Object
SQL
NoSQL

Graphical user interfaces

GTK+ GIMP Toolkit
FLTK

Programming tools

Configuration management and source code management

CVS
Git
RCS
• LibreSource Synchronizer


Make
Rake
Cabal
Ant
CADES
Nant
Maven
• Final Builder
Gradle
• Visual Build Pro



Parser creation tools

Yacc/Bison


Libraries
Design languages
Patterns, document many common programming and project management techniques
Processes and methodologies

• Agile

Scrum

• Heavyweight

ISO/IEC 12207 — software life cycle processes

• Process Models

CMM and CMMI/SCAMPI
ISO 15504 (SPICE)

• Metamodels

SPEM

Platforms

A platform combines computer hardware and an operating system. As platforms grow more powerful and less costly, applications and tools grow more widely available.

BREW
Classic Mac OS and macOS PCs
Windows PCs (Wintel)

Other Practices
Other tools
Computer science topics

Skilled software engineers know a lot of computer science including what is possible and impossible, and what is easy and hard for software.

Algorithms, well-defined methods for solving specific problems.

Sorting
Parsing


Yacc/Bison

Data structures, well-defined methods for storing and retrieving data.

Lists
Trees

Computability, some problems cannot be solved at all


Complexity, some problems are solvable in principle, yet unsolvable in practice






Mathematics topics
Life cycle phases


Testing, detects bugs


Quality assurance, ensures compliance with process.

Product Life cycle phase and Project lifecycle

• Inception
• First development
• Major release
• Bug fix release
• Maintenance

Release development stage, near the end of a release cycle

Alpha
Beta
1.0; 2.0


SSADM
V-model
DSDM

Deliverables

Deliverables must be developed for many SE projects. Software engineers rarely make all of these deliverables themselves. They usually cooperate with the writers, trainers, installers, marketers, technical support people, and others who make many of these deliverables.

• Application software — the software
Database — schemas and data.
Documentation, online and/or print, FAQ, Readme, release notes, Help, for each role

User
Manager
Buyer

• Administration and Maintenance policy, what should be backed-up, checked, configured, ...
• Migration

• Upgrade from previous installations
• Upgrade from competitor's installations

Training materials, for each role

User
• Administrator
Manager
Buyer

Support info for computer support groups.
Marketing and sales materials

White papers, explain the technologies used in the applications

Business roles

• Operations

Users
• Administrators
Buyers

• Development

Testers


Consulting — customization and installation of applications
Sales
Legal — contracts, intellectual property rights
Support — helping customers use applications
Personnel — hiring and training qualified personnel
Finance — funding new development



Management topics


Vision, SEs are good at this
• Example, everyone follows a good example best


Hiring, getting people into an organization


• Customer interaction (Rethink)


Metrics

Business topics
Software engineering profession
History of software engineering
Pioneers

Many people made important contributions to SE technologies, practices, or applications.

John Backus: Fortran, first optimizing compiler, BNF
Victor Basili: Experience factory.
F.L. Bauer: Stack principle, popularized the term Software Engineering
Edsger Dijkstra: Wrote Notes on Structured Programming, A Discipline of Programming and Go To Statement Considered Harmful, algorithms, formal methods, pedagogy.
Adele Goldstine: Wrote the Operators Manual for the ENIAC, the first electronic digital computer, and trained some of the first human computers
Lois Haibt: FORTRAN, wrote the first parser
Margaret Hamilton: Coined the term "software engineering", developed Universal Systems Language
Mary Jean Harrold: Regression testing, fault localization
Grace Hopper: The first compiler (Mark 1), COBOL, Nanoseconds.
Bill Joy: Berkeley Unix, vi, Java.
Brian Kernighan: C and Unix.
Nancy Leveson: System safety
Peter G. Neumann: RISKS Digest, ACM Sigsoft.
David Parnas: Module design, social responsibility, professionalism.
Jef Raskin: Developed the original Macintosh GUI, authored The Humane Interface
Mary Shaw: Software architecture.
Linus Torvalds: Linux kernel, free software / open source development.
• Will Tracz: Reuse, ACM Software Engineering Notes.
Elaine Weyuker: Software testing

See also


Notable publications

About Face: The Essentials of User Interface Design by Alan Cooper, about user interface design. ISBN 0-7645-2641-3
The Capability Maturity Model by Watts Humphrey. Written for the Software Engineering Institute, emphasizing management and process. (See Managing the Software Process ISBN 0-201-18095-2)
The Cathedral and the Bazaar by Eric Raymond about open source development.
The Decline and Fall of the American Programmer by Ed Yourdon predicts the end of software development in the U.S. ISBN 0-13-191958-X
Extreme Programming Explained by Kent Beck ISBN 0-321-27865-8
• "Go To Statement Considered Harmful" by Edsger Dijkstra.
• "Internet, Innovation and Open Source:Actors in the Network" — First Monday article by Ilkka Tuomi (2000) source
The Mythical Man-Month by Fred Brooks, about project management. ISBN 0-201-83595-9
Object-oriented Analysis and Design by Grady Booch. ISBN 0-8053-5340-2
Peopleware by Tom DeMarco and Tim Lister. ISBN 0-932633-43-9
The pragmatic engineer versus the scientific designer by E. W. Dijkstra [1]
Principles of Software Engineering Management by Tom Gilb about evolutionary processes. ISBN 0-201-19246-2
The Psychology of Computer Programming by Gerald Weinberg. Written as an independent consultant, partly about his years at IBM. ISBN 0-932633-42-0
Refactoring: Improving the Design of Existing Code by Martin Fowler, Kent Beck, John Brant, William Opdyke, and Don Roberts. ISBN 0-201-48567-2
The Pragmatic Programmer: from journeyman to master by Andrew Hunt, and David Thomas. ISBN 0-201-61622-X
Software Engineering Body of Knowledge (SWEBOK) ISO/IEC TR 19759

Related fields
See also
References

cite-note-11. citerefbourquedupuis2004Bourque, Pierre; Dupuis, Robert, eds. (2004). Guide to the Software Engineering Body of Knowledge - 2004 Version. IEEE Computer Society. p. 1. ISBN 0-7695-2330-7.

External links

• ACM Computing Classification System
• Guide to the Software Engineering Body of Knowledge (SWEBOK)

Professional organizations

• British Computer Society
• Association for Computing Machinery
• IEEE Computer Society

Professionalism

• SE Code of Ethics
• Professional licensing in Texas

Education

• CCSE Undergraduate curriculum

Standards

• IEEE Software Engineering Standards
• Internet Engineering Task Force
• ISO

Government organizations

• European Software Institute
• Software Engineering Institute

Agile

• Organization to promote Agile software development
• Test driven development
• Extreme programming

Other organizations

• Online community for software engineers
• Software Engineering Society

Demographics

• U.S. Bureau of Labor Statistics on SE

Surveys

• David Redmiles page from the University of California site

Other

• Full text in PDF from the NATO conference in Garmisch
• Computer Risks Peter G. Neumann's risks column.